We have seen four different metrics for achitecture and we have seen in what area they have any influence on how the code of the software system is going to be. We have discussed Cyclometic Complexity, objects without a name and/or a type, Cohesion and Coupling. Three of these have influence on the complexity of the software system and one has the potential to make the architecture less comprehensible.

We have seen that complexity is of influence on the maintainability of the software system, because most of the metrics we have seen have influence on complexity you can make sure that during the creation of the architecture you can get the Cyclometic Complexity, Cohesion and Coupling optimised for low Cyclometic Complexity in the code.

Ofcourse objects without a name and or type should be avoided alltogether.

Finally we should say that measuring metrics on architecture is only usefull when the architecture of a software system is as complete as possible. In practice it often happens that only parts of the system are fully modelled and some parts are only vaguely described. This means that when the architecture in not complete the metrics on architecture are often not representable for the maintainability of your system.